SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Precision Time Protocol</title>

</head>

Precision Time Protocol

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .infobox-subbox{padding:0;border:none;margin:-3px;width:auto;min-width:100%;font-size:100%;clear:none;float:none;background-color:transparent}.mw-parser-output .infobox-3cols-child{margin:auto}.mw-parser-output .infobox .navbar{font-size:100%}@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media(min-width:640px){body.skin--responsive .mw-parser-output .infobox-table{display:table!important}body.skin--responsive .mw-parser-output .infobox-table>caption{display:table-caption!important}body.skin--responsive .mw-parser-output .infobox-table>tbody{display:table-row-group}body.skin--responsive .mw-parser-output .infobox-table th,body.skin--responsive .mw-parser-output .infobox-table td{padding-left:inherit;padding-right:inherit}}

/* end https://en.wikipedia.org/ */

</style><table class="infobox vevent" style="width:26em;"><caption class="infobox-title summary">Precision Time Protocol</caption><tbody><tr><td colspan="2" class="infobox-subheader"><a href="Communication_protocol" title="Communication protocol">Communication protocol</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Abbreviation</th><td class="infobox-data">PTP</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Purpose</th><td class="infobox-data">Time</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Developer(s)</th><td class="infobox-data"><a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Introduction</th><td class="infobox-data">2002 (2002)</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;"><a href="Port_(computer_networking)" title="Port (computer networking)">Port(s)</a></th><td class="infobox-data">udp/319, udp/320</td></tr></tbody></table>

The Precision Time Protocol (PTP) is a <a href="Protocol_(computing)" class="mw-redirect" title="Protocol (computing)">protocol</a> for <a href="Clock_synchronization" title="Clock synchronization">clock synchronization</a> throughout a <a href="Computer_network" title="Computer network">computer network</a> with relatively high <a href="Accuracy_and_precision" title="Accuracy and precision">precision</a> and therefore potentially high accuracy. In a <a href="Local_area_network" title="Local area network">local area network</a> (LAN), accuracy can be sub-microsecond – making it suitable for measurement and control systems.<a href="#cite_note-1">[1]</a> PTP is used to synchronize <a href="Financial_transaction" title="Financial transaction">financial transactions</a>, <a href="Mobile_phone_tower" class="mw-redirect" title="Mobile phone tower">mobile phone tower</a> transmissions, sub-sea <a href="Acoustic_array" class="mw-redirect" title="Acoustic array">acoustic arrays</a>, and networks that require precise timing but lack access to <a href="Satellite_navigation" title="Satellite navigation">satellite navigation</a> signals.

The first version of PTP, IEEE 1588-2002, was published in 2002. IEEE 1588-2008, also known as PTP Version 2, is not <a href="Backward_compatible" class="mw-redirect" title="Backward compatible">backward compatible</a> with the 2002 version. IEEE 1588-2019 was published in November 2019 and includes backward-compatible improvements to the 2008 publication. IEEE 1588-2008 includes a profile concept defining PTP operating parameters and options. Several profiles have been defined for applications including <a href="Telecommunications" title="Telecommunications">telecommunications</a>, <a href="Electric_power_distribution" title="Electric power distribution">electric power distribution</a> and <a href="Audiovisual" title="Audiovisual">audiovisual</a> uses. <style data-mw-deduplicate="TemplateStyles:r1238216509">

/* start https://en.wikipedia.org/ */

.mw-parser-output .vanchor>:target~.vanchor-text{background-color:#b1d2ff}@media screen{html.skin-theme-clientpref-night .mw-parser-output .vanchor>:target~.vanchor-text{background-color:#0f4dc9}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .vanchor>:target~.vanchor-text{background-color:#0f4dc9}}

/* end https://en.wikipedia.org/ */

</style>IEEE 802.1AS is an adaptation of PTP, called gPTP, for use with <a href="Audio_Video_Bridging" title="Audio Video Bridging">Audio Video Bridging</a> (AVB) and <a href="Time-Sensitive_Networking" title="Time-Sensitive Networking">Time-Sensitive Networking</a> (TSN).

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

According to John Eidson, who led the IEEE 1588-2002 standardization effort, "IEEE 1588 is designed to fill a niche not well served by either of the two dominant protocols, <a href="Network_Time_Protocol" title="Network Time Protocol">NTP</a> and <a href="GPS" class="mw-redirect" title="GPS">GPS</a>. IEEE 1588 is designed for local systems requiring accuracies beyond those attainable using NTP. It is also designed for applications that cannot bear the cost of a <a href="GPS_receiver" class="mw-redirect" title="GPS receiver">GPS receiver</a> at each node, or for which GPS signals are inaccessible."<a href="#cite_note-Eidson-2">[2]</a>

PTP was originally defined in the IEEE 1588-2002 standard, officially titled Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, and published in 2002. In 2008, IEEE 1588-2008 was released as a revised standard; also known as PTP version 2 (PTPv2), it improves accuracy, precision and robustness but is not <a href="Backward_compatible" class="mw-redirect" title="Backward compatible">backward compatible</a> with the original 2002 version.<a href="#cite_note-Eidson2-3">[3]</a> IEEE 1588-2019 was published in November 2019,<a href="#cite_note-4">[4]</a> is informally known as PTPv2.1 and includes backwards-compatible improvements to the 2008 publication.<a href="#cite_note-Arnold_2017-5">[5]</a>

<div class="mw-heading mw-heading2"><h2 id="Architecture">Architecture</h2></div>

The IEEE 1588 standards describe a <a href="Hierarchy" title="Hierarchy">hierarchical</a> <a href="Master/slave_(technology)" class="mw-redirect" title="Master/slave (technology)">master–slave architecture</a> for clock <a href="Distributed_computing" title="Distributed computing">distribution</a> consisting of one or more <a href="Network_segment" title="Network segment">network segments</a> and one or more clocks. An ordinary clock is a device with a single network connection that is either the source of or the destination for a synchronization reference. A source is called a master (alternately timeTransmitter<a href="#cite_note-IEEE_1588g-6">[6]</a>), and a destination is called a slave (alternately timeReceiver<a href="#cite_note-IEEE_1588g-6">[6]</a>). A boundary clock has multiple network connections and synchronizes one network segment to another. A single, synchronization leader is selected, a.k.a. elected, for each network segment. The root timing reference is called the grandmaster.<a href="#cite_note-7">[7]</a>

A relatively simple PTP architecture consists of ordinary clocks on a single-segment network with no boundary clocks. A grandmaster is elected and all other clocks synchronize to it.

IEEE 1588-2008 introduces a clock associated with network equipment used to convey PTP messages. The transparent clock modifies PTP messages as they pass through the device.<a href="#cite_note-TI2013-8">[8]</a> <a href="Timestamps" class="mw-redirect" title="Timestamps">Timestamps</a> in the messages are corrected for time spent traversing the network equipment. This scheme improves distribution accuracy by compensating for <a href="Packet_delay_variation" title="Packet delay variation">delivery variability</a> across the network.

PTP typically uses the same <a href="Epoch_(computing)" title="Epoch (computing)">epoch</a> as <a href="Unix_time" title="Unix time">Unix time</a> (start of 1 January 1970).<a href="#cite_note-10">[a]</a> While the Unix time is based on <a href="Coordinated_Universal_Time" title="Coordinated Universal Time">Coordinated Universal Time</a> (UTC) and is subject to <a href="Leap_second" title="Leap second">leap seconds</a>, PTP is based on <a href="International_Atomic_Time" title="International Atomic Time">International Atomic Time</a> (TAI). The PTP grandmaster communicates the current offset between UTC and TAI, so that UTC can be computed from the received PTP time.

<div class="mw-heading mw-heading2"><h2 id="Protocol_details">Protocol details</h2></div>

Synchronization and management of a PTP system is achieved through the exchange of messages across the communications medium. To this end, PTP uses the following message types.

<ul><li>Sync, Follow_Up, Delay_Req and Delay_Resp messages are used by ordinary and boundary clocks and communicate time-related information used to synchronize clocks across the network.</li>

<li>Pdelay_Req, Pdelay_Resp and Pdelay_Resp_Follow_Up are used by transparent clocks to measure delays across the communications medium so that they can be compensated for by the system. Transparent clocks and these messages associated with them are not available in original IEEE 1588-2002 PTPv1 standard, and were added in PTPv2.</li>

<li>Announce messages are used by the <a href="#Best_master_clock_algorithm">best master clock algorithm</a> in IEEE 1588-2008 to build a clock hierarchy and select the grandmaster.<a href="#cite_note-11">[b]</a></li>

<li>Management messages are used by <a href="Network_management" title="Network management">network management</a> to monitor, configure and maintain a PTP system.</li>

<li>Signaling messages are used for non-time-critical communications between clocks. Signaling messages were introduced in IEEE 1588-2008.</li></ul>

Messages are categorized as event and general messages. Event messages are time-critical in that accuracy in transmission and receipt timestamp accuracy directly affects clock distribution accuracy. Sync, Delay_Req, Pdelay_Req and Pdelay_resp are event messages. General messages are more conventional <a href="Protocol_data_units" class="mw-redirect" title="Protocol data units">protocol data units</a> in that the data in these messages is of importance to PTP, but their transmission and receipt timestamps are not. Announce, Follow_Up, Delay_Resp, Pdelay_Resp_Follow_Up, Management and Signaling messages are members of the general message class.<a href="#cite_note-1588-2008-9">[9]</a>: Clause 6.4

<div class="mw-heading mw-heading3"><h3 id="Message_transport">Message transport</h3></div>

PTP messages may use the <a href="User_Datagram_Protocol" title="User Datagram Protocol">User Datagram Protocol</a> over <a href="Internet_Protocol" title="Internet Protocol">Internet Protocol</a> (UDP/IP) for transport. IEEE 1588-2002 uses only <a href="IPv4" title="IPv4">IPv4</a> transports,<a href="#cite_note-1588-2002-12">[10]</a>: Annex D but this has been extended to include <a href="IPv6" title="IPv6">IPv6</a> in IEEE 1588-2008.<a href="#cite_note-1588-2008-9">[9]</a>: Annex F In IEEE 1588-2002, all PTP messages are sent using <a href="Multicast" title="Multicast">multicast</a> messaging, while IEEE 1588-2008 introduced an option for devices to negotiate <a href="Unicast" title="Unicast">unicast</a> transmission on a port-by-port basis.<a href="#cite_note-1588-2008-9">[9]</a>: Clause 16.1 Multicast transmissions use <a href="IP_multicast" title="IP multicast">IP multicast</a> addressing, for which multicast group addresses are defined for IPv4 and IPv6 (see table).<a href="#cite_note-1588-2008-9">[9]</a>: Annex D and E Time-critical event messages (Sync, Delay_req, Pdelay_Req and Pdelay_Resp) are sent to <a href="Port_number" class="mw-redirect" title="Port number">port number</a> 319. General messages (Announce, Follow_Up, Delay_Resp, Pdelay_Resp_Follow_Up, management and signaling) use port number 320.<a href="#cite_note-1588-2008-9">[9]</a>: Clause 6.4

<caption>Multicast group addresses

</caption>

<th>Messages

</th>

<th>IPv4

</th>

<th>IPv6

</th>

<th>IEEE 802.3 Ethernet<a href="#cite_note-1588-2008-9">[9]</a>: Annex F <a href="#cite_note-13">[c]</a>

</th>

<th>Type

</th></tr>

<tr>

<td>All except peer delay messages

</td>

</td>

</td>

</td>

<td>Forwardable

</td></tr>

<tr>

<td>Peer delay messages: Pdelay_Req, Pdelay_Resp and Pdelay_Resp_Follow_Up<a href="#cite_note-17">[g]</a>

</td>

</td>

<td>FF02::6B

</td>

<td>01-80-C2-00-00-0E

</td>

<td>Non-forwardable

</td></tr></tbody></table>

In IEEE 1588-2008, encapsulation is also defined for <a href="DeviceNet" title="DeviceNet">DeviceNet</a>,<a href="#cite_note-1588-2008-9">[9]</a>: Annex G <a href="ControlNet" title="ControlNet">ControlNet</a><a href="#cite_note-1588-2008-9">[9]</a>: Annex H and <a href="PROFINET" class="mw-redirect" title="PROFINET">PROFINET</a>.<a href="#cite_note-1588-2008-9">[9]</a>: Annex I

<div class="mw-heading mw-heading3"><h3 id="Domains">Domains</h3></div>

A domain<a href="#cite_note-19">[i]</a> is an interacting set of clocks that synchronize to one another using PTP. Clocks are assigned to a domain by virtue of the contents of the Subdomain name (IEEE 1588-2002) or the domainNumber (IEEE 1588-2008) fields in PTP messages they receive or generate. Domains allow multiple clock distribution systems to share the same communications medium.

<th>Subdomain name field contents (IEEE1588-2002)

</th>

<th>IPv4 multicast address (IEEE1588-2002)<a href="#cite_note-20">[j]</a>

</th>

<th>domainNumber (IEEE1588-2008)

</th>

<th>Notes

</th></tr>

<tr>

<td>_DFLT

</td>

<td>224.0.1.129

</td>

<td>0

</td>

<td>Default domain

</td></tr>

<tr>

<td>_ALT1

</td>

<td>224.0.1.130

</td>

<td>1

</td>

<td>Alternate domain 1

</td></tr>

<tr>

<td>_ALT2

</td>

<td>224.0.1.131

</td>

<td>2

</td>

<td>Alternate domain 2

</td></tr>

<tr>

<td>_ALT3

</td>

<td>224.0.1.132

</td>

<td>3

</td>

<td>Alternate domain 3

</td></tr>

<tr>

<td>Application specific up to 15 octets<a href="#cite_note-1588-2002-12">[10]</a>: Clause 6.2.5.1

</td>

<td>224.0.1.130, 131 or 132 as per <a href="Hash_function" title="Hash function">hash function</a> on Subdomain name<a href="#cite_note-1588-2002-12">[10]</a>: Annex C

</td>

<td>4 through 127

</td>

<td>User-defined domains

</td></tr></tbody></table>

<div class="mw-heading mw-heading2"><h2 id="Best_master_clock_algorithm">Best master clock algorithm</h2></div>

The best master clock algorithm (BMCA) performs a distributed selection of the best clock to act as leader based on the following clock properties:

<ul><li>Identifier – A universally unique numeric identifier for the clock. This is typically constructed based on a device's <a href="MAC_address" title="MAC address">MAC address</a>.</li>

<li>Quality – Both versions of IEEE 1588 attempt to quantify clock quality based on expected timing deviation, technology used to implement the clock or location in a <a href="Clock_stratum" class="mw-redirect" title="Clock stratum">clock stratum</a> schema, although only V1 (IEEE 1588-2002) knows a data field stratum. PTP V2 (IEEE 1588-2008) defines the overall quality of a clock by using the data fields clockAccuracy and clockClass.</li>

<li>Priority – An administratively assigned precedence hint used by the BMCA to help select a grandmaster for the PTP domain. IEEE 1588-2002 used a single <a href="Boolean_variable" class="mw-redirect" title="Boolean variable">Boolean variable</a> to indicate precedence. IEEE 1588-2008 features two 8-bit priority fields.</li>

<li>Variance – A clock's estimate of its stability based on observation of its performance against the PTP reference.</li></ul>

IEEE 1588-2008 uses a hierarchical selection algorithm based on the following properties, in the indicated order:<a href="#cite_note-1588-2008-9">[9]</a>: Figure 27

<ol><li>Priority 1 – the user can assign a specific static-designed priority to each clock, preemptively defining a priority among them. Smaller numeric values indicate higher priority.</li>

<li>Class – each clock is a member of a given class, each class getting its own priority.</li>

<li>Accuracy – precision between clock and UTC, in nanoseconds (ns)</li>

<li>Variance – variability of the clock</li>

<li>Priority 2 – final-defined priority, defining backup order in case the other criteria were not sufficient. Smaller numeric values indicate higher priority.</li>

<li>Unique identifier – MAC address-based selection is used as a tiebreaker when all other properties are equal.</li></ol>

IEEE 1588-2002 uses a selection algorithm based on similar properties.

Clock properties are advertised in IEEE 1588-2002 Sync messages and in IEEE 1588-2008 Announce messages. The current leader transmits this information at regular interval. A clock that considers itself a better leader will transmit this information in order to invoke a change of leader. Once the current leader recognizes the better clock, the current leader stops transmitting Sync messages and associated clock properties (Announce messages in the case of IEEE 1588-2008) and the better clock takes over as leader.<a href="#cite_note-21">[11]</a> The BMCA only considers the self-declared quality of clocks and does not take network link quality into consideration.<a href="#cite_note-22">[12]</a>

<div class="mw-heading mw-heading2"><h2 id="Synchronization">Synchronization</h2></div>

Via BMCA, PTP selects a source of time for an IEEE 1588 domain and for each network segment in the domain.

Clocks determine the offset between themselves and their leader.<a href="#cite_note-IEC-23">[13]</a> Let the variable <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle t}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle t}</annotation>

</semantics>

</math><img src="./65658b7b223af9e1acc877d848888ecdb4466560.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.338ex; width:0.84ex; height:2.009ex;" alt="{\displaystyle t}" loading="lazy"> represent physical time. For a given follower device, the offset <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle o(t)}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle o(t)}</annotation>

</semantics>

</math><img src="./241c8f555002b4df57e79ce53ee57227fafb5f47.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.838ex; width:3.777ex; height:2.843ex;" alt="{\displaystyle o(t)}" loading="lazy"> at time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle t}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle t}</annotation>

</semantics>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle \ o(t)=s(t)-m(t)}</annotation>

</semantics>

</math><img src="./b31dc1a597e1e906f8dad2dcc855dd632c36d707.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.838ex; width:18.725ex; height:2.843ex;" alt="{\displaystyle \ o(t)=s(t)-m(t)}" loading="lazy"></dd></dl>

where <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle s(t)}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle s(t)}</annotation>

</semantics>

</math><img src="./c484de351ba40ccb9a5ad522c29c1aac5686c0df.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.838ex; width:3.739ex; height:2.843ex;" alt="{\displaystyle s(t)}" loading="lazy"> represents the time measured by the follower clock at physical time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle t}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle t}</annotation>

</semantics>

</math><img src="./65658b7b223af9e1acc877d848888ecdb4466560.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.338ex; width:0.84ex; height:2.009ex;" alt="{\displaystyle t}" loading="lazy">, and <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle m(t)}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle m(t)}</annotation>

</semantics>

</math><img src="./ea26578dd72bf4dbc3fa391c9feb11eed495699b.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.838ex; width:4.689ex; height:2.843ex;" alt="{\displaystyle m(t)}" loading="lazy"> represents the time measured by the leader clock at physical time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle t}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle t}</annotation>

</semantics>

The leader periodically broadcasts the current time as a message to the other clocks. Under IEEE 1588-2002 broadcasts are up to once per second. Under IEEE 1588-2008, up to 10 per second are permitted.

Each broadcast begins at time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{1}}">

<msub>

</mrow>

</msub>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{1}}</annotation>

</semantics>

</math><img src="./2f304724948a3ef606c4a92459e22b87a954d993.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.671ex; width:2.412ex; height:2.509ex;" alt="{\displaystyle T_{1}}" loading="lazy"> with a Sync message sent by the leader to all the clocks in the domain. A clock receiving this message takes note of the local time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{1}'}">

</mrow>

</msubsup>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{1}'}</annotation>

</semantics>

The leader may subsequently send a multicast Follow_Up with accurate <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{1}}">

<msub>

</mrow>

</msub>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{1}}</annotation>

</semantics>

</math><img src="./2f304724948a3ef606c4a92459e22b87a954d993.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.671ex; width:2.412ex; height:2.509ex;" alt="{\displaystyle T_{1}}" loading="lazy"> timestamp. Not all leaders have the ability to present an accurate timestamp in the Sync message. It is only after the transmission is complete that they are able to retrieve an accurate timestamp for the Sync transmission from their network hardware. Leaders with this limitation use the Follow_Up message to convey <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{1}}">

<msub>

</mrow>

</msub>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{1}}</annotation>

</semantics>

In order to accurately synchronize to their leader, clocks must individually determine the network transit time of the Sync messages. The transit time is determined indirectly by measuring round-trip time from each clock to its leader. The clocks initiate an exchange with their leader designed to measure the transit time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle d}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle d}</annotation>

</semantics>

</math><img src="./e85ff03cbe0c7341af6b982e47e9f90d235c66ab.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.338ex; width:1.216ex; height:2.176ex;" alt="{\displaystyle d}" loading="lazy">. The exchange begins with a clock sending a Delay_Req message at time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{2}}">

<msub>

</mrow>

</msub>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{2}}</annotation>

</semantics>

</math><img src="./d1ba5f12fbb0ff766aec6e22148b429373608555.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.671ex; width:2.412ex; height:2.509ex;" alt="{\displaystyle T_{2}}" loading="lazy"> to the leader. The leader receives and timestamps the Delay_Req at time <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{2}'}">

</mrow>

</msubsup>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{2}'}</annotation>

</semantics>

</math><img src="./3be30a7034a4cf80eb1d4f05ac8995d188a5c66e.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -1.005ex; width:2.412ex; height:2.843ex;" alt="{\displaystyle T_{2}'}" loading="lazy"> and responds with a Delay_Resp message. The leader includes the timestamp <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{2}'}">

</mrow>

</msubsup>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{2}'}</annotation>

</semantics>

Through these exchanges a clock learns <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{1}}">

<msub>

</mrow>

</msub>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{1}}</annotation>

</semantics>

</mrow>

</msubsup>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{1}'}</annotation>

</semantics>

</math><img src="./ac58e22462fc1aeef6a80d3f5649af0a52fcbdc1.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -1.005ex; width:2.412ex; height:2.843ex;" alt="{\displaystyle T_{1}'}" loading="lazy">, <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{2}}">

<msub>

</mrow>

</msub>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{2}}</annotation>

</semantics>

</math><img src="./d1ba5f12fbb0ff766aec6e22148b429373608555.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.671ex; width:2.412ex; height:2.509ex;" alt="{\displaystyle T_{2}}" loading="lazy"> and <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle T_{2}'}">

</mrow>

</msubsup>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle T_{2}'}</annotation>

</semantics>

If <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle d}">

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle d}</annotation>

</semantics>

</math><img src="./e85ff03cbe0c7341af6b982e47e9f90d235c66ab.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.338ex; width:1.216ex; height:2.176ex;" alt="{\displaystyle d}" loading="lazy"> is the transit time for the Sync message, and <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle {\tilde {o}}}">

<mover>

</mover>

</mrow>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle {\tilde {o}}}</annotation>

</semantics>

</math><img src="./c204684c345609a5985599bb3961a82744a19023.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.338ex; width:1.292ex; height:2.176ex;" alt="{\displaystyle {\tilde {o}}}" loading="lazy"> is the constant offset between leader and follower clocks, then

</mrow>

</msubsup>

<msub>

</mrow>

</msub>

<mover>

</mover>

</mrow>

</mrow>

</mrow>

</msubsup>

<msub>

</mrow>

</msub>

<mover>

</mover>

</mrow>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle \ T_{1}'-T_{1}={\tilde {o}}+d{\text{ and }}\ T_{2}'-T_{2}=-{\tilde {o}}+d}</annotation>

</semantics>

</math><img src="./bfa91ba13375614a95bf79703b0ff95548ff08e3.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -1.005ex; width:40.099ex; height:2.843ex;" alt="{\displaystyle \ T_{1}'-T_{1}={\tilde {o}}+d{\text{ and }}\ T_{2}'-T_{2}=-{\tilde {o}}+d}" loading="lazy"></dd></dl>

Combining the above two equations, we find that

<mover>

</mover>

</mrow>

<mfrac>

</mfrac>

</mrow>

</mrow>

</msubsup>

<msub>

</mrow>

</msub>

</mrow>

</msubsup>

<msub>

</mrow>

</msub>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle {\tilde {o}}={\frac {1}{2}}(T_{1}'-T_{1}-T_{2}'+T_{2})}</annotation>

</semantics>

</math><img src="./018b5557d5e574ab310648a27acad17b2439e0da.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -1.838ex; width:26.366ex; height:5.176ex;" alt="{\displaystyle {\tilde {o}}={\frac {1}{2}}(T_{1}'-T_{1}-T_{2}'+T_{2})}" loading="lazy"></dd></dl>

The clock now knows the offset <math xmlns="http://www.w3.org/1998/Math/MathML" alttext="{\displaystyle {\tilde {o}}}">

<mover>

</mover>

</mrow>

</mstyle>

</mrow>

<annotation encoding="application/x-tex">{\displaystyle {\tilde {o}}}</annotation>

</semantics>

</math><img src="./c204684c345609a5985599bb3961a82744a19023.svg" class="mwe-math-fallback-image-inline mw-invert skin-invert" aria-hidden="true" style="vertical-align: -0.338ex; width:1.292ex; height:2.176ex;" alt="{\displaystyle {\tilde {o}}}" loading="lazy"> during this transaction and can correct itself by this amount to bring it into agreement with their leader.

One assumption is that this exchange of messages happens over a period of time so small that this offset can safely be considered constant over that period. Another assumption is that the transit time of a message going from the leader to a follower is equal to the transit time of a message going from the follower to the leader. Finally, it is assumed that both the leader and follower can accurately measure the time they send or receive a message. The degree to which these assumptions hold true determines the accuracy of the clock at the follower device.<a href="#cite_note-1588-2008-9">[9]</a>: Clause 6.2

<div class="mw-heading mw-heading2"><h2 id="Optional_features">Optional features</h2></div>

IEEE 1588-2008 standard lists the following set of features that implementations may choose to support:

<ul><li>Alternate Time-Scale</li>

<li>Grand Master Cluster</li>

<li>Unicast Masters</li>

<li>Alternate Master</li>

<li>Path Trace</li></ul>

IEEE 1588-2019 adds additional optional and backward-compatible features:<a href="#cite_note-Arnold_2017-5">[5]</a>

<ul><li>Modular transparent clocks</li>

<li>Special PTP ports to interface with transports with built-in time distribution</li>

<li>Unicast Delay_Req and Delay_Resp messages</li>

<li>Manual port configuration overriding BMCA</li>

<li>Asymmetry calibration</li>

<li>Ability to utilize a physical layer frequency reference (e.g. <a href="Synchronous_Ethernet" title="Synchronous Ethernet">Synchronous Ethernet</a>)</li>

<li>Profile isolation</li>

<li>Inter-domain interactions</li>

<li>Security TLV for integrity checking</li>

<li>Standard performance reporting metrics</li>

<li>Slave port monitoring</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Related_initiatives">Related initiatives</h2></div>

<ul><li>The International IEEE Symposium on Precision Clock Synchronization for Measurement, Control and Communication (ISPCS) is an IEEE-organized annual event that includes a <a href="Plugtest" title="Plugtest">plugtest</a> and a conference program with paper and poster presentations, tutorials and discussions covering several aspects of PTP.<a href="#cite_note-24">[14]</a></li>

<li>The Institute of Embedded Systems (InES) of the <a href="Zurich_University_of_Applied_Sciences/ZHAW" title="Zurich University of Applied Sciences/ZHAW">Zurich University of Applied Sciences/ZHAW</a> is addressing the practical implementation and application of PTP.</li>

<li>IEEE 1588 is a key technology in the <a href="LXI" class="mw-redirect" title="LXI">LXI</a> Standard for Test and Measurement communication and control.</li>

<li>IEEE 802.1AS-2011 is part of the IEEE <a href="Audio_Video_Bridging" title="Audio Video Bridging">Audio Video Bridging</a> (AVB) group of standards.<a href="#cite_note-25">[k]</a> It specifies a profile for use of IEEE 1588-2008 for time synchronization over a virtual bridged local area network as defined by <a href="IEEE_802.1Q" title="IEEE 802.1Q">IEEE 802.1Q</a>. In particular, 802.1AS defines how <a href="IEEE_802.3" title="IEEE 802.3">IEEE 802.3</a> (<a href="Ethernet" title="Ethernet">Ethernet</a>), <a href="IEEE_802.11" title="IEEE 802.11">IEEE 802.11</a> (<a href="Wi-Fi" title="Wi-Fi">Wi-Fi</a>), and <a href="Multimedia_over_Coax_Alliance" title="Multimedia over Coax Alliance">MoCA</a> can all be parts of the same PTP timing domain.<a href="#cite_note-26">[15]</a></li>

<li><a href="SMPTE_2059" title="SMPTE 2059">SMPTE 2059</a>-2 is a PTP profile for use in synchronization of broadcast media systems.<a href="#cite_note-27">[16]</a></li>

<li>The <a href="AES67" title="AES67">AES67</a> audio networking interoperability standard includes a PTPv2 profile compatible with SMPTE ST2059-2.<a href="#cite_note-28">[17]</a></li>

<li><a href="Dante_(networking)" title="Dante (networking)">Dante</a> uses PTPv1 for synchronization.<a href="#cite_note-coveloz2016-29">[18]</a></li>

<li><a href="Q-LAN" title="Q-LAN">Q-LAN</a><a href="#cite_note-30">[19]</a> and <a href="Ravenna_(networking)" title="Ravenna (networking)">RAVENNA</a><a href="#cite_note-coveloz2016-29">[18]</a> use PTPv2 for time synchronization.</li>

<li><a href="The_White_Rabbit_Project" class="mw-redirect" title="The White Rabbit Project">The White Rabbit Project</a> combines <a href="Synchronous_Ethernet" title="Synchronous Ethernet">Synchronous Ethernet</a> and PTP.</li>

<li><a href="Precision_Time_Protocol_Industry_Profile" title="Precision Time Protocol Industry Profile">Precision Time Protocol Industry Profile</a> PTP profiles (L2P2P and L3E2E) for industrial automation in IEC 62439-3</li>

<li><a href="IEC/IEEE_61850-9-3" title="IEC/IEEE 61850-9-3">IEC/IEEE 61850-9-3</a> PTP profile for substation automation adopted by IEC 61850</li>

<li><a href="Parallel_Redundancy_Protocol" title="Parallel Redundancy Protocol">Parallel Redundancy Protocol</a> use of PTP profiles (L2P2P and L3E2E) for industrial automation in parallel networks</li>

<li>PTP is being studied to be applied as a secure time synchronization protocol in power systems' Wide Area Monitoring<a href="#cite_note-31">[20]</a></li></ul>

<ul><li><a href="List_of_PTP_implementations" title="List of PTP implementations">List of PTP implementations</a> – Systems supporting Precision Time Protocol</li>

<li><a href="Real-time_communication" title="Real-time communication">Real-time communication</a> – Protocols and communication hardware that give real-time guarantees</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-lower-alpha">

<li id="cite_note-10"><a href="#cite_ref-10">^</a> The profile capability under IEEE 1588-2008 allows the use of application-specific epochs.<a href="#cite_note-1588-2008-9">[9]</a>: Annex B

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> In IEEE 1588-2002, information carried by Announce messages is carried in the Sync messages. In IEEE 1588-2008, the Sync message has been optimized and this information is no longer carried here.

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> PTP over bare IEEE 802.3 Ethernet using <a href="Ethertype" class="mw-redirect" title="Ethertype">Ethertype</a> 0x88F7

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> IEEE 1588-2002 non-default domains use destination addresses 224.0.1.130 through 224.0.1.132 (see <a href="#Domains">#Domains</a>).

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> Where x is the address scope (2 for link-local) as per RFC 2373 (see <a href="Multicast_address#IPv6" title="Multicast address">IPv6 multicast address</a>)

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> In some PTP applications it is permissible to send all PTP messages to 01-1B-19-00-00-00

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> Peer delay messages are intended to propagate to the immediately connected neighbor. The multicast addresses for these messages are designed to be link-local in scope and are not passed through a <a href="Router_(computing)" title="Router (computing)">router</a>. IEEE 1588-2008 also recommends setting <a href="Time_to_live" title="Time to live">time to live</a> to 1 (IPv4) or hop limit to 0 (IPv6) as further insurance that the messages will not be routed.

</li>

<li id="cite_note-18"><a href="#cite_ref-18">^</a> Peer delay messaging is not present in IEEE 1588-2002

</li>

<li id="cite_note-19"><a href="#cite_ref-19">^</a> IEEE 1588-2002 defines a domain as any interconnected set of clocks (regardless of whether they synchronized to one another) and uses subdomain to refer to what is known as a domain in IEEE 1588-2008.

</li>

<li id="cite_note-20"><a href="#cite_ref-20">^</a> IEEE 1588-2008 uses 224.0.1.129 as the address for all multicast messages.

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> AVB is further extended by the IEEE 802.1 <a href="Time-Sensitive_Networking" title="Time-Sensitive Networking">Time-Sensitive Networking</a> (TSN) Task Group.

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFEidson2005" class="citation web cs1">Eidson, John (10 October 2005). <a rel="nofollow" class="external text" href="https://www.nist.gov/document/tutorial-basicpdf">"IEEE-1588 Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, a Tutorial"</a>. National Institute of Standards and Technology (NIST).</cite>

</li>

<li id="cite_note-Eidson-2"><a href="#cite_ref-Eidson_2-0">^</a> <cite id="CITEREFEidson2006" class="citation book cs1">Eidson, John C. (April 2006). Measurement, Control and Communication Using IEEE 1588. <a href="Springer_Science%2BBusiness_Media" title="Springer Science+Business Media">Springer</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-84628-250-8</bdi>.</cite>

</li>

<li id="cite_note-Eidson2-3"><a href="#cite_ref-Eidson2_3-0">^</a> <cite id="CITEREFEidson2006" class="citation web cs1">Eidson, John (2 October 2006). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100331083017/http://ieee1588.nist.gov/2006%20IEEE1588%20Agenda/Eidson_1588_Version%202.pdf">"IEEE 1588 Standard Version 2 - A Tutorial"</a> (PDF). Archived from <a rel="nofollow" class="external text" href="http://ieee1588.nist.gov/2006%20IEEE1588%20Agenda/Eidson_1588_Version%202.pdf">the original</a> (PDF) on 31 March 2010. Retrieved 12 June 2008.</cite>

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://standards.ieee.org/ieee/1588/6825/">"1588-2019 - IEEE Approved Draft Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems"</a>. IEEE. Retrieved 15 February 2020.</cite>

</li>

<li id="cite_note-Arnold_2017-5">^ <a href="#cite_ref-Arnold_2017_5-0">a</a> <a href="#cite_ref-Arnold_2017_5-1">b</a> <cite id="CITEREFDouglas_Arnold2017" class="citation web cs1">Douglas Arnold (24 September 2017). <a rel="nofollow" class="external text" href="https://blog.meinbergglobal.com/2017/09/24/whats-coming-next-edition-ieee-1588/">"What's coming In the Next Edition of IEEE 1588?"</a>. Retrieved 15 February 2020.</cite>

</li>

<li id="cite_note-IEEE_1588g-6">^ <a href="#cite_ref-IEEE_1588g_6-0">a</a> <a href="#cite_ref-IEEE_1588g_6-1">b</a> <cite class="citation cs2">IEEE 1588g-2022 Amendment 2: Master-Slave Optional Alternative Terminology, <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a>, 3 December 2022</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20100527161310/http://ieee1588.nist.gov/terms.htm">"Meanings of common terms used in IEEE 1588"</a>. National Institute of Standards and Technology. Archived from <a rel="nofollow" class="external text" href="http://ieee1588.nist.gov/terms.htm">the original</a> on 27 May 2010. Retrieved 19 May 2006.</cite>

</li>

<li id="cite_note-TI2013-8"><a href="#cite_ref-TI2013_8-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.ti.com/lit/an/snla104a/snla104a.pdf">"AN-1838 IEEE 1588 Boundary Clock and Transparent Clock Implementation Using the DP83640"</a> (PDF). ti.com. Texas Instruments. Retrieved 17 July 2019.</cite>

</li>

<li id="cite_note-1588-2008-9">^ <a href="#cite_ref-1588-2008_9-0">a</a> <a href="#cite_ref-1588-2008_9-1">b</a> <a href="#cite_ref-1588-2008_9-2">c</a> <a href="#cite_ref-1588-2008_9-3">d</a> <a href="#cite_ref-1588-2008_9-4">e</a> <a href="#cite_ref-1588-2008_9-5">f</a> <a href="#cite_ref-1588-2008_9-6">g</a> <a href="#cite_ref-1588-2008_9-7">h</a> <a href="#cite_ref-1588-2008_9-8">i</a> <a href="#cite_ref-1588-2008_9-9">j</a> <a href="#cite_ref-1588-2008_9-10">k</a> <a href="#cite_ref-1588-2008_9-11">l</a> <cite class="citation cs2">IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a>, 24 July 2008, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FIEEESTD.2008.4579760">10.1109/IEEESTD.2008.4579760</a>, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-7381-5400-8</bdi></cite>

</li>

<li id="cite_note-1588-2002-12">^ <a href="#cite_ref-1588-2002_12-0">a</a> <a href="#cite_ref-1588-2002_12-1">b</a> <a href="#cite_ref-1588-2002_12-2">c</a> <cite class="citation cs2">IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a>, 8 November 2002, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FIEEESTD.2002.94144">10.1109/IEEESTD.2002.94144</a>, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-7381-3369-0</bdi></cite>

</li>

<li id="cite_note-21"><a href="#cite_ref-21">^</a> <cite id="CITEREFWattAchantaAbubakariSagen2014" class="citation cs2">Watt, Steve T.; Achanta, Shankar; Abubakari, Hamza; Sagen, Eric (March 2014), <a rel="nofollow" class="external text" href="https://cdn.selinc.com/assets/Literature/Publications/Technical%20Papers/6650_UnderstandingApplying_SA_20140206_Web3.pdf">Understanding and Applying Precision Time Protocol</a> (PDF), retrieved 9 September 2017</cite>

</li>

<li id="cite_note-22"><a href="#cite_ref-22">^</a> <cite id="CITEREFFSMLabs_Technical_Staff2015" class="citation cs2">FSMLabs Technical Staff (September 2015), <a rel="nofollow" class="external text" href="http://www.fsmlabs.com/news/2015/09/18/socalledbestmasterclock.html">Smart and Dumb PTP Client and the "so-called"Best Master Clock Algorithm</a>, retrieved 17 May 2018</cite>

</li>

<li id="cite_note-IEC-23"><a href="#cite_ref-IEC_23-0">^</a> <a href="International_standard" title="International standard">International standard</a> <a href="IEC" class="mw-redirect" title="IEC">IEC</a> 61588: Precision clock synchronization protocol for networked measurement and control systems. 2004.

</li>

<li id="cite_note-24"><a href="#cite_ref-24">^</a> <a rel="nofollow" class="external text" href="http://www.ispcs.org">ISPCS website</a>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite id="CITEREFGeoffrey_M._Garner2010" class="citation cs2">Geoffrey M. Garner (28 May 2010), <a rel="nofollow" class="external text" href="https://www.itu.int/dms_pub/itu-t/oth/06/38/T06380000040002PDFE.pdf">IEEE 802.1AS and IEEE 1588</a> (PDF)</cite>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <cite class="citation cs2"><a rel="nofollow" class="external text" href="https://www.smpte.org/news-events/news-releases/smpte%C2%AE-publishes-first-two-parts-standard-enabling-deployment-ptp-timed">SMPTE Publishes First Two Parts of Standard Enabling Deployment of PTP-Timed Equipment in Existing SDI Plants</a>, <a href="Society_of_Motion_Picture_and_Television_Engineers" title="Society of Motion Picture and Television Engineers">Society of Motion Picture and Television Engineers</a>, 13 April 2015, retrieved 21 May 2015</cite>

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> <cite class="citation cs2"><a rel="nofollow" class="external text" href="http://www.aes.org/publications/standards/search.cfm?docID=105">AES-R16-2016: AES Standards Report - PTP parameters for AES67 and SMPTE ST 2059-2 interoperability</a>, <a href="Audio_Engineering_Society" title="Audio Engineering Society">Audio Engineering Society</a>, 2 May 2016</cite>

</li>

<li id="cite_note-coveloz2016-29">^ <a href="#cite_ref-coveloz2016_29-0">a</a> <a href="#cite_ref-coveloz2016_29-1">b</a> <a rel="nofollow" class="external free" href="https://www.smpte.org/sites/default/files/users/user27446/AES67%20for%20Audio%20Production-Background%20Applications%20and%20Challenges.pdf">https://www.smpte.org/sites/default/files/users/user27446/AES67%20for%20Audio%20Production-Background%20Applications%20and%20Challenges.pdf</a>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <cite id="CITEREFOyen2017" class="citation web cs1">Oyen, Seppe (6 June 2017). <a rel="nofollow" class="external text" href="https://www.luminex.be/improve-your-timekeeping-with-ptpv2/">"PTPv2 Timing protocol in AV networks"</a>. Luminex. <q>Q-LAN updated to PTPv2 approximately two years ago.</q></cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite id="CITEREFPepicielloVaccaro2018" class="citation cs2">Pepiciello, Antonio; Vaccaro, Alfredo (17 December 2018), "A reliable architecture based on Precision Time Protocol for WAMPAC synchronization", 2018 AEIT International Annual Conference, <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a>, pp. 1–5, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.23919%2FAEIT.2018.8577414">10.23919/AEIT.2018.8577414</a>, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-8-8872-3740-5</bdi>, <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:58819556">58819556</a></cite>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20131206102327/http://www.zhaw.ch/en/engineering/institutes-centres/ines/downloads/documents.html">PTP documentation at InES</a></li>

<li><a rel="nofollow" class="external text" href="https://www.albedotelecom.com/src/lib/WP-Mobile-PTP.pdf">PTP and Synchronization of LTE mobile networks</a></li>

<li><a rel="nofollow" class="external text" href="https://www.albedotelecom.com/src/lib/WP-PTP.pdf">PTP explained under the installation / maintenance point of view</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110818184219/http://www.belden.com/pdfs/Techpprs/Precision_Clock_Synchronization_WP.pdf">Hirschmann PTP Whitepaper</a></li>

<li><a rel="nofollow" class="external text" href="https://www.cisco.com/c/en/us/td/docs/switches/connectedgrid/cgs2520/software/release/12_2_58_ey/configuration/cgs_2520_swcg.html#wp1988925">PTP overview in Cisco CGS 2520 Switch Software Configuration Guide</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20160304192052/http://www.bcit.ca/files/appliedresearch/pdf/ruggedcom_industry.pdf">Perspectives and priorities on RuggedCom Smart Grid Research IEC 61850 Technologies</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120114222001/http://xn--61850-txen0l.xn--p1ai/wp-content/plugins/downloads-manager/upload/Introduction%20of%20Smart%20Subsltation%20Projects.pdf">Projects with Smart Substation Solution</a></li>

<li><cite id="CITEREFMcGheeGoraj2010" class="citation cs2">McGhee, Jim; Goraj, Maciej (2010), "Smart High Voltage Substation Based on IEC 61850 Process Bus and IEEE 1588 Time Synchronization", 2010 First IEEE International Conference on Smart Grid Communications, pp. 489–494, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FSMARTGRID.2010.5622092">10.1109/SMARTGRID.2010.5622092</a>, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4244-6510-1</bdi>, <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:30638718">30638718</a></cite></li>

<li><cite id="CITEREFIngramCampbellSchaubLedwich2011" class="citation book cs1">Ingram, D.M.E; Campbell, D.A.; Schaub, P.; Ledwich, G.F. (2011). <a rel="nofollow" class="external text" href="https://eprints.qut.edu.au/41257/">"Test and evaluation system for multi-protocol sampled value protection schemes"</a>. 2011 IEEE Trondheim PowerTech. Trondheim, Norway: IEEE. pp. 1–7. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FPTC.2011.6019243">10.1109/PTC.2011.6019243</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4244-8419-5</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:42991214">42991214</a>.</cite></li>

<li><a rel="nofollow" class="external text" href="https://safran-navigation-timing.com/solution/white-rabbit-solutions/">The White Rabbit Project PTP</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20170205095756/http://lamspeople.epfl.ch/kirrmann/Pubs/IEC_62439-3/PacWorld_038_043_IEC_IEEE_61850-9-3_September_2016_HK.pdf">IEC&IEEE Precision Time Protocol</a>, Pacworld, September 2016</li>

<li><a rel="nofollow" class="external text" href="https://webstore.iec.ch/publication/24447">IEC 62439-3 Annexes A-E Redundant attachment of clocks and network management</a></li>

<li><a rel="nofollow" class="external text" href="https://www.luminex.be/improve-your-timekeeping-with-ptpv2-2/">PTPv2 Timing protocol in AV networks</a></li>

<li><a rel="nofollow" class="external text" href="https://www.fsmlabs.com/news/2016/03/31/singlesource.html">FSMLabs: Single source IEEE PTP 1588 cannot meet financial regulatory standards</a></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="IEEE_standards209" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="IEEE_standards209" style="font-size:114%;margin:0 4em"><a href="IEEE_Standards_Association" title="IEEE Standards Association">IEEE standards</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Current</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="IEEE_754-2008_revision" title="IEEE 754-2008 revision">Revision</a></li></ul></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802" title="IEEE 802">802 series</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802" title="IEEE 802">802</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="WiMAX" title="WiMAX">WiMAX · d · e</a></li></ul></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.1" title="IEEE 802.1">802.1</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.3" title="IEEE 802.3">802.3</a> (<a href="Ethernet" title="Ethernet">Ethernet</a>)</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.11" title="IEEE 802.11">802.11</a> (<a href="Wi-Fi" title="Wi-Fi">Wi-Fi</a>)</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="IEEE_802.11_(legacy_mode)" title="IEEE 802.11 (legacy mode)">legacy mode</a></li>

<li><a href="IEEE_802.11ad" title="IEEE 802.11ad">ad</a> (<a href="WiGig" title="WiGig">WiGig</a>)</li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.15" title="IEEE 802.15">802.15</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="IEEE_802.15.1" class="mw-redirect" title="IEEE 802.15.1">.1</a> (<a href="Bluetooth" title="Bluetooth">Bluetooth</a>)</li>

<li><a href="IEEE_802.15.4" title="IEEE 802.15.4">.4</a> (<a href="Zigbee" title="Zigbee">Zigbee</a>)</li>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Proposed</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Superseded</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li> Category</li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-06-15" href="https://en.wikipedia.org/wiki/?title=Precision_Time_Protocol&oldid=1295728177">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>